SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Function model</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Function model</span></span>

</h1>

</header>

In <a href="Systems_engineering" title="Systems engineering">systems engineering</a>, <a href="Software_engineering" title="Software engineering">software engineering</a>, and <a href="Computer_science" title="Computer science">computer science</a>, a <b>function model</b> or <b>functional model</b> is a structured representation of the <a href="Function_(engineering)" title="Function (engineering)">functions</a> (<a href="Activity_diagram" title="Activity diagram">activities</a>, <a href="Task_analysis" title="Task analysis">actions</a>, <a href="https://en.wiktionary.org/wiki/process" class="extiw external" title="wikt:process">processes</a>, <a href="Operations_management" title="Operations management">operations</a>) within the modeled <a href="System" title="System">system</a> or subject area.<sup id="cite_ref-ITL93_1-0" class="reference"><a href="#cite_note-ITL93-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> </p>

<p>A function model, similar with the <a href="Activity_diagram" title="Activity diagram">activity model</a> or <a href="Process_model" class="mw-redirect" title="Process model">process model</a>, is a graphical representation of an <a href="Business" title="Business">enterprise</a>'s function within a defined scope. The purposes of the function model are to describe the functions and processes, assist with discovery of information needs, help identify opportunities, and establish a basis for determining product and service costs.<sup id="cite_ref-rmsc-1995_2-0" class="reference"><a href="#cite_note-rmsc-1995-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>The function model in the field of systems engineering and software engineering originates in the 1950s and 1960s, but the origin of functional modelling of organizational activity goes back to the late 19th century.

</p><p>In the late 19th century the first diagrams appeared that pictured business activities, actions, processes, or operations, and in the first half of the 20th century the first structured methods for documenting business process activities emerged. One of those methods was the <a href="Flow_process_chart" title="Flow process chart">flow process chart</a>, introduced by <a href="Frank_Gilbreth" class="mw-redirect" title="Frank Gilbreth">Frank Gilbreth</a> to members of <a href="American_Society_of_Mechanical_Engineers" title="American Society of Mechanical Engineers">American Society of Mechanical Engineers</a> (ASME) in 1921 with the presentation, entitled “Process Charts—First Steps in Finding the One Best Way”.<sup id="cite_ref-BBG02_3-0" class="reference"><a href="#cite_note-BBG02-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> Gilbreth's tools quickly found their way into <a href="Industrial_engineering" title="Industrial engineering">industrial engineering</a> curricula.

</p><p>The emergence of the field of <i>systems engineering</i> can be traced back to <a href="Bell_Labs" title="Bell Labs">Bell Telephone Laboratories</a> in the 1940s.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> The need to identify and manipulate the properties of a system as a whole, which in complex engineering projects may greatly differ from the sum of the parts' properties, motivated various industries to apply the discipline.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> One of the first to define the function model in this field was the British engineer <a href="William_Gosling_(engineer)" title="William Gosling (engineer)">William Gosling</a>. In his book <i>The design of engineering systems</i> (1962, p. 25) he stated:

</p>

<dl><dd><i>A functional model must thus achieve two aims in order to be of use. It must furnish a throughput description mechanics capable of completely defining the first and last throughput states, and perhaps some of the intervening states. It must also offer some means by which any input, correctly described in terms of this mechanics, can be used to generate an output which is an equally correct description of the output which the actual system would have given for the input concerned. It may also be noted that there are two other things which a functional model may do, but which are not necessary to all functional models. Thus such a system may, but need not, describe the system throughputs other than at the input and output, and it may also contain a description of the operation which each element carries out on the throughput, but once again this is not.</i><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup></dd></dl>

<p>One of the first well defined function models, was the <a href="Functional_flow_block_diagram" title="Functional flow block diagram">functional flow block diagram</a> (FFBD) developed by the defense-related <a href="TRW_Inc." title="TRW Inc.">TRW</a> Incorporated in the 1950s.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> In the 1960s it was exploited by the <a href="NASA" title="NASA">NASA</a> to visualize the time sequence of events in a space systems and flight missions.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> It is further widely used in classical <a href="Systems_engineering" title="Systems engineering">systems engineering</a> to show the order of execution of system functions.<sup id="cite_ref-TD03_9-0" class="reference"><a href="#cite_note-TD03-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Functional_modeling_topics">Functional modeling topics</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Functional_perspective">Functional perspective</h3></div>

<p>In <a href="Systems_engineering" title="Systems engineering">systems engineering</a> and <a href="Software_engineering" title="Software engineering">software engineering</a> a function model is created with a functional <a href="Modeling_perspectives" class="mw-redirect" title="Modeling perspectives">modeling perspective</a>. The functional perspective is one of the perspectives possible in <a href="Business_process_modelling" class="mw-redirect" title="Business process modelling">business process modelling</a>, other perspectives are for example behavioural, organisational or informational.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p><p>A functional modeling perspective concentrates on describing the <a href="Dynamic_system" class="mw-redirect" title="Dynamic system">dynamic process</a>. The main concept in this modeling perspective is the process, this could be a function, transformation, activity, action, task etc. A well-known example of a modeling language employing this perspective is <a href="Data_flow_diagram" class="mw-redirect" title="Data flow diagram">data flow diagrams</a>.

</p><p>The perspective uses four symbols to describe a process, these being:

</p>

<ul><li>Process: Illustrates transformation from input to output.</li>

<li>Store: Data-collection or some sort of material.</li>

<li>Flow: Movement of data or material in the process.</li>

<li>External Entity: External to the modeled system, but interacts with it.</li></ul>

<p>Now, with these symbols, a process can be represented as a network of these symbols. This decomposed process is a DFD, data flow diagram.

</p>

<p>In <a href="Dynamic_Enterprise_Modeling" class="mw-redirect" title="Dynamic Enterprise Modeling">Dynamic Enterprise Modeling</a> a division is made in the Control model, Function Model, <a href="Process_model" class="mw-redirect" title="Process model">Process model</a> and Organizational model.

</p><div class="mw-heading mw-heading3"><h3 id="Functional_decomposition">Functional decomposition</h3></div>

<p><a href="Functional_decomposition" title="Functional decomposition">Functional decomposition</a> refers broadly to the process of resolving a <a href="Function_(mathematics)" title="Function (mathematics)">functional</a> relationship into its constituent parts in such a way that the original function can be reconstructed from those parts by <a href="Function_composition" title="Function composition">function composition</a>. In general, this process of decomposition is undertaken either for the purpose of gaining insight into the identity of the constituent components, or for the purpose of obtaining a compressed representation of the global function, a task which is feasible only when the constituent processes possess a certain level of <i>modularity</i>.

</p><p><a href="Decomposition_(computer_science)" title="Decomposition (computer science)">Functional decomposition</a> has a prominent role in <a href="Computer_programming" title="Computer programming">computer programming</a>, where a major goal is to <i>modularize</i> processes to the greatest extent possible. For example, a library management system may be broken up into an inventory module, a patron information module, and a fee assessment module. In the early decades of computer programming, this was manifested as the "art of subroutining," as it was called by some prominent practitioners.

</p><p>Functional decomposition of engineering systems is a method for analyzing engineered systems. The basic idea is to try to divide a system in such a way that each block of the block diagram can be described without an "and" or "or" in the description.

</p><p>This exercise forces each part of the system to have a pure <a href="Role" title="Role">function</a>. When a system is composed of pure functions, they can be reused, or replaced. A usual side effect is that the interfaces between blocks become simple and generic. Since the interfaces usually become simple, it is easier to replace a pure function with a related, similar function.

</p>

<div class="mw-heading mw-heading2"><h2 id="Functional_modeling_methods">Functional modeling methods</h2></div>

<p>The functional approach is extended in multiple diagrammic techniques and modeling notations. This section gives an overview of the important techniques in chronological order.

</p>

<div class="mw-heading mw-heading3"><h3 id="Function_block_diagram">Function block diagram</h3></div>

<p>A <a href="Functional_block_diagram" title="Functional block diagram">functional block diagram</a> is a <a href="Block_diagram" title="Block diagram">block diagram</a>, that describes the functions and interrelationships of a <a href="System" title="System">system</a>. The functional block diagram can picture:<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li>Functions of a system pictured by blocks</li>

<li>Input of a block pictured with lines, and</li>

<li>Relationships between 9 functions</li>

<li>Functional sequences and paths for matter and or signals<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup></li></ul>

<p>The block diagram can use additional schematic symbols to show particular properties.

</p><p>Specific function block diagram are the classic <a href="Functional_flow_block_diagram" title="Functional flow block diagram">functional flow block diagram</a>, and the <a href="Function_Block_Diagram" class="mw-redirect" title="Function Block Diagram">Function Block Diagram</a> (FBD) used in the design of <a href="Programmable_logic_controller" title="Programmable logic controller">programmable logic controllers</a>.

</p>

<div class="mw-heading mw-heading3"><h3 id="Functional_flow_block_diagram">Functional flow block diagram</h3></div>

<p>The <a href="Functional_flow_block_diagram" title="Functional flow block diagram">functional flow block diagram</a> (FFBD) is a multi-tier, time-sequenced, step-by-step <a href="Flow_diagram" title="Flow diagram">flow diagram</a> of the <a href="System" title="System">system</a>'s functional flow.<sup id="cite_ref-faa.gov_14-0" class="reference"><a href="#cite_note-faa.gov-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup>

The diagram is developed in the 1950s and widely used in classical <a href="Systems_engineering" title="Systems engineering">systems engineering</a>. The functional flow block diagram is also referred to as <i>Functional Flow Diagram</i>, <i>functional block diagram</i>, and <i>functional flow</i>.<sup id="cite_ref-FAA08_15-0" class="reference"><a href="#cite_note-FAA08-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>

</p><p>Functional flow block diagrams (FFBD) usually define the detailed, step-by-step operational and support sequences for <a href="System" title="System">systems</a>, but they are also used effectively to define <a href="https://en.wiktionary.org/wiki/process" class="extiw external" title="wikt:process">processes</a> in developing and producing systems. The <a href="Software_development_process" title="Software development process">software development processes</a> also use FFBDs extensively. In the system context, the functional flow steps may include combinations of <a href="Computer_hardware" title="Computer hardware">hardware</a>, <a href="Software" title="Software">software</a>, <a href="Personnel" class="mw-redirect" title="Personnel">personnel</a>, facilities, and/or procedures.

</p><p>In the FFBD method, the functions are organized and depicted by their logical order of execution. Each function is shown with respect to its logical relationship to the execution and completion of other functions. A node labeled with the function name depicts each function. Arrows from left to right show the order of execution of the functions. Logic symbols represent sequential or parallel execution of functions.<sup id="cite_ref-FAA06_16-0" class="reference"><a href="#cite_note-FAA06-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup>

</p>

<p><a href="HIPO" class="mw-redirect" title="HIPO">HIPO</a> for <i>hierarchical input process output</i> is a popular 1970s <a href="Systems_analysis" title="Systems analysis">systems analysis</a> design aid and documentation technique<sup id="cite_ref-17" class="reference"><a href="#cite_note-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup> for representing the modules of a <a href="System" title="System">system</a> as a <a href="Hierarchy" title="Hierarchy">hierarchy</a> and for documenting each module.<sup id="cite_ref-Sandia92_18-0" class="reference"><a href="#cite_note-Sandia92-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup>

</p><p>It was used to develop requirements, construct the design, and support implementation of an expert system to demonstrate automated rendezvous. Verification was then conducted systematically because of the method of design and implementation.<sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup>

</p><p>The overall design of the system is documented using HIPO charts or <a href="Structure_chart" title="Structure chart">structure charts</a>. The structure chart is similar in appearance to an organizational chart, but has been modified to show additional detail. Structure charts can be used to display several types of information, but are used most commonly to diagram either <a href="Data_structure" title="Data structure">data structures</a> or code structures.<sup id="cite_ref-Sandia92_18-1" class="reference"><a href="#cite_note-Sandia92-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="N2_Chart">N<sup>2</sup> Chart</h3></div>

<p>The <a href="N2_Chart" class="mw-redirect" title="N2 Chart">N<sup>2</sup> Chart</a> is a diagram in the shape of a <a href="Matrix_(mathematics)" title="Matrix (mathematics)">matrix</a>, representing functional or physical interfaces between system elements. It is used to systematically identify, define, tabulate, design, and analyze functional and physical interfaces. It applies to system <a href="Interface_(computing)" title="Interface (computing)">interfaces</a> and <a href="Computer_hardware" title="Computer hardware">hardware</a> and/or <a href="Software" title="Software">software</a> interfaces.<sup id="cite_ref-faa.gov_14-1" class="reference"><a href="#cite_note-faa.gov-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup>

</p><p>The N<sup>2</sup> diagram has been used extensively to develop data interfaces, primarily in the <a href="Software" title="Software">software</a> areas. However, it can also be used to develop hardware interfaces. The basic N<sup>2</sup> chart is shown in Figure 2. The system functions are placed on the diagonal; the remainder of the squares in the N × N matrix represent the interface inputs and outputs.

</p>

<div class="mw-heading mw-heading3"><h3 id="Structured_Analysis_and_Design_Technique">Structured Analysis and Design Technique</h3></div>

<p><a href="Structured_Analysis_and_Design_Technique" class="mw-redirect" title="Structured Analysis and Design Technique">Structured Analysis and Design Technique</a> (SADT) is a <a href="Software_engineering_methodology" class="mw-redirect" title="Software engineering methodology">software engineering methodology</a> for describing <a href="System" title="System">systems</a> as a hierarchy of functions, a <a href="Diagram" title="Diagram">diagrammatic</a> notation for constructing a sketch for a software application. It offers building blocks to represent entities and activities, and a variety of arrows to relate boxes. These boxes and arrows have an associated informal <a href="Semantics" title="Semantics">semantics</a>.<sup id="cite_ref-JM04_21-0" class="reference"><a href="#cite_note-JM04-21"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup> SADT can be used as a functional analysis tool of a given process, using successive levels of details. The SADT method allows to define user needs for IT developments, which is used in industrial Information Systems, but also to explain and to present an activity's manufacturing processes, procedures.<sup id="cite_ref-FL_22-0" class="reference"><a href="#cite_note-FL-22"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup>

</p><p>The SADT supplies a specific functional view of any enterprise by describing the functions and their relationships in a company. These functions fulfill the objectives of a company, such as sales, order planning, product design, part manufacturing, and human resource management. The SADT can depict simple functional relationships and can reflect data and control flow relationships between different functions. The <a href="IDEF0" title="IDEF0">IDEF0</a> formalism is based on SADT, developed by <a href="Douglas_T._Ross" title="Douglas T. Ross">Douglas T. Ross</a> in 1985.<sup id="cite_ref-23" class="reference"><a href="#cite_note-23"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup>

</p>

<p><a href="IDEF0" title="IDEF0">IDEF0</a> is a <a href="Function_modeling" class="mw-redirect" title="Function modeling">function modeling</a> methodology for describing <a href="Manufacturing" title="Manufacturing">manufacturing</a> functions, which offers a functional <a href="Modeling_language" title="Modeling language">modeling language</a> for the analysis, development, re-engineering, and integration of <a href="Information_system" title="Information system">information systems</a>; business processes; or software engineering analysis.<sup id="cite_ref-DAC01_24-0" class="reference"><a href="#cite_note-DAC01-24"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup> It is part of the <a href="IDEF" title="IDEF">IDEF</a> family of modeling languages in the field of <a href="Software_engineering" title="Software engineering">software engineering</a>, and is built on the functional modeling language building <a href="Structured_analysis_and_design_technique" title="Structured analysis and design technique">SADT</a>.

</p><p>The IDEF0 Functional Modeling method is designed to model the decisions, actions, and activities of an organization or system.<sup id="cite_ref-VG00_25-0" class="reference"><a href="#cite_note-VG00-25"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup> It was derived from the established graphic modeling language <a href="Structured_analysis_and_design_technique" title="Structured analysis and design technique">structured analysis and design technique</a> (SADT) developed by <a href="Douglas_T._Ross" title="Douglas T. Ross">Douglas T. Ross</a> and <a href="SofTech%2C_Inc." class="mw-redirect" title="SofTech, Inc.">SofTech, Inc.</a> In its original form, IDEF0 includes both a definition of a graphical modeling language (<a href="Syntax" title="Syntax">syntax</a> and <a href="Semantics" title="Semantics">semantics</a>) and a description of a comprehensive methodology for developing models.<sup id="cite_ref-ITL93_1-1" class="reference"><a href="#cite_note-ITL93-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> The US Air Force commissioned the SADT developers to develop a function model method for analyzing and communicating the functional perspective of a system. IDEF0 should assist in organizing system analysis and promote effective communication between the analyst and the customer through simplified graphical devices.<sup id="cite_ref-VG00_25-1" class="reference"><a href="#cite_note-VG00-25"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Axiomatic_design">Axiomatic design</h3></div>

<p><a href="Axiomatic_design" title="Axiomatic design">Axiomatic design</a> is a top down hierarchical functional decomposition process used as a solution synthesis framework for the analysis, development, re-engineering, and integration of products, information systems, business processes or software engineering solutions.<sup id="cite_ref-AD_26-0" class="reference"><a href="#cite_note-AD-26"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup> Its structure is suited mathematically to analyze coupling between functions in order to optimize the architectural robustness of potential functional solution models.

</p>

<div class="mw-heading mw-heading2"><h2 id="Related_types_of_models">Related types of models</h2></div>

<p>In the field of systems and software engineering numerous specific function and functional models and close related models have been defined. Here only a few general types will be explained.

</p>

<div class="mw-heading mw-heading3"><h3 id="Business_function_model">Business function model</h3></div>

<p>A <i>Business Function Model</i> (BFM) is a general description or category of operations performed routinely to carry out an organization's mission. They "provide a conceptual structure for the identification of general <a href="Business_function" class="mw-redirect" title="Business function">business functions</a>".<sup id="cite_ref-27" class="reference"><a href="#cite_note-27"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup> It can show the critical <a href="Business_process" title="Business process">business processes</a> in the context of the business area functions. The processes in the business function model must be consistent with the processes in the value chain models. Processes are a group of related business activities performed to produce an end product or to provide a service. Unlike business functions that are performed on a continual basis, processes are characterized by the fact that they have a specific beginning and an end point marked by the delivery of a desired output. The figure on the right depicts the relationship between the business processes, business functions, and the business area's business reference model.<sup id="cite_ref-28" class="reference"><a href="#cite_note-28"><span class="cite-bracket">[</span>28<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Business_Process_Model_and_Notation">Business Process Model and Notation</h3></div>

<p><a href="Business_Process_Model_and_Notation" title="Business Process Model and Notation">Business Process Model and Notation</a> (BPMN) is a <a href="Information_visualisation" class="mw-redirect" title="Information visualisation">graphical representation</a> for specifying <a href="Business_process" title="Business process">business processes</a> in a <a href="Workflow" title="Workflow">workflow</a>. BPMN was developed by <a href="Business_Process_Management_Initiative" class="mw-redirect" title="Business Process Management Initiative">Business Process Management Initiative</a> (BPMI), and is currently maintained by the <a href="Object_Management_Group" title="Object Management Group">Object Management Group</a> since the two organizations merged in 2005. The current version of BPMN is 2.0.<sup id="cite_ref-bpmifaq_29-0" class="reference"><a href="#cite_note-bpmifaq-29"><span class="cite-bracket">[</span>29<span class="cite-bracket">]</span></a></sup>

</p><p>The Business Process Model and Notation (BPMN) specification provides a graphical notation for specifying <a href="Business_process" title="Business process">business processes</a> in a Business Process Diagram (BPD).<sup id="cite_ref-30" class="reference"><a href="#cite_note-30"><span class="cite-bracket">[</span>30<span class="cite-bracket">]</span></a></sup> The objective of BPMN is to support business process management for both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics. The BPMN specification also provides a mapping between the graphics of the notation to the underlying constructs of execution languages, particularly <a href="BPEL4WS" class="mw-redirect" title="BPEL4WS">BPEL4WS</a>.<sup id="cite_ref-31" class="reference"><a href="#cite_note-31"><span class="cite-bracket">[</span>31<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Business_reference_model">Business reference model</h3></div>

<p>A <a href="Business_reference_model" title="Business reference model">Business reference model</a> is a reference model, concentrating on the functional and organizational aspects of the <a href="Core_business" title="Core business">core business</a> of an <a href="Business" title="Business">enterprise</a>, <a href="Tertiary_sector_of_the_economy" title="Tertiary sector of the economy">service organization</a> or <a href="Government_agency" title="Government agency">government agency</a>. In enterprise engineering a business reference model is part of an <a href="Enterprise_Architecture_Framework" class="mw-redirect" title="Enterprise Architecture Framework">Enterprise Architecture Framework</a> or <i>Architecture Framework</i>, which defines how to organize the structure and <a href="View_model" title="View model">views</a> associated with an <a href="Enterprise_Architecture" class="mw-redirect" title="Enterprise Architecture">Enterprise Architecture</a>.

</p><p>A <a href="Reference_model" title="Reference model">reference model</a> in general is a model of something that embodies the basic goal or idea of something and can then be looked at as a reference for various purposes. A business reference model is a means to describe the business operations of an organization, independent of the <a href="Organizational_structure" title="Organizational structure">organizational structure</a> that perform them. Other types of business reference model can also depict the relationship between the <a href="Business_process" title="Business process">business processes</a>, business functions, and the <a href="Business_area" class="mw-redirect" title="Business area">business area</a>'s business reference model. These reference model can be constructed in layers, and offer a foundation for the analysis of service components, technology, data, and performance.

</p>

<div class="mw-heading mw-heading3"><h3 id="Operator_function_model">Operator function model</h3></div>

<p>The <i>Operator Function Model</i> (OFM) is proposed as an alternative to traditional <a href="Task_analysis" title="Task analysis">task analysis</a> techniques used by <a href="Human_factors" class="mw-redirect" title="Human factors">human factors</a> engineers. An operator function model attempts to represent in mathematical form how an operator might decompose a complex system into simpler parts and coordinate control actions and system configurations so that acceptable overall system performance is achieved. The model represents basic issues of knowledge representation, information flow, and decision making in complex systems. Miller (1985) suggests that the network structure can be thought of as a possible representation of an operator's <a href="Mental_model" title="Mental model">internal model</a> of the system plus a control structure which specifies how the model is used to solve the decision problems that comprise operator control functions.<sup id="cite_ref-32" class="reference"><a href="#cite_note-32"><span class="cite-bracket">[</span>32<span class="cite-bracket">]</span></a></sup>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <span style="font-weight: bold; font-style: italic;"><a href="https://commons.wikimedia.org/wiki/Category:Function_models" class="extiw external" title="commons:Category:Function models">Function models</a></span>.</div></div>

</div>

<ul><li><a href="Bus_Functional_Model" class="mw-redirect" title="Bus Functional Model">Bus Functional Model</a></li>

<li><a href="Business_process_modeling" title="Business process modeling">Business process modeling</a></li>

<li><a href="Data_and_information_visualization" title="Data and information visualization">Data and information visualization</a></li>

<li><a href="Data_model" title="Data model">Data model</a></li>

<li><a href="Enterprise_modeling" class="mw-redirect" title="Enterprise modeling">Enterprise modeling</a></li>

<li><a href="Functional_Software_Architecture" class="mw-redirect" title="Functional Software Architecture">Functional Software Architecture</a></li>

<li><a href="Multilevel_Flow_Modeling" title="Multilevel Flow Modeling">Multilevel Flow Modeling</a></li>

<li><a href="Polynomial_and_rational_function_modeling#Polynomial_function_models" title="Polynomial and rational function modeling">Polynomial function model</a></li>

<li><a href="Polynomial_and_rational_function_modeling#Rational_function_models" title="Polynomial and rational function modeling">Rational function model</a></li>

<li><a href="Scientific_modeling" class="mw-redirect" title="Scientific modeling">Scientific modeling</a></li>

<li><a href="Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a></li>

<li><a href="View_model" title="View model">View model</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<p><span class="noviewer" typeof="mw:File"><span></span></span> This article incorporates <a href="Copyright_status_of_works_by_the_federal_government_of_the_United_States" title="Copyright status of works by the federal government of the United States">public domain material</a> from the <a rel="nofollow" class="external text" href="https://www.nist.gov">National Institute of Standards and Technology</a>

</p><p><span class="noviewer" typeof="mw:File"><span></span></span> This article incorporates <a href="Copyright_status_of_works_by_the_federal_government_of_the_United_States" title="Copyright status of works by the federal government of the United States">public domain material</a> from <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation cs1"><a rel="nofollow" class="external text" href="https://www.hf.faa.gov/Workbenchtools/default.aspx?rPage=Tooldetails&subCatId=28&toolID=192"><i>Operator Function Model (OFM)</i></a>. <a href="Federal_Aviation_Administration" title="Federal Aviation Administration">Federal Aviation Administration</a>.</cite>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

<li id="cite_note-ITL93-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-ITL93_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-ITL93_1-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.itl.nist.gov/fipspubs/idef02.doc">FIPS Publication 183</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090227122140/http://www.itl.nist.gov/fipspubs/idef02.doc">Archived</a> 2009-02-27 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> released of IDEFØ December 1993 by the Computer Systems Laboratory of the National Institute of Standards and Technology (NIST).</span>

</li>

<li id="cite_note-rmsc-1995-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-rmsc-1995_2-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.archives.gov/era/pdf/rmsc-19951006-dod-rm-function-and-information-models.pdf">Reader's Guide to IDEF0 Function Models</a>. Accessed 27 Nov 2008.</span>

</li>

<li id="cite_note-BBG02-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-BBG02_3-0">^</a></b></span> <span class="reference-text">Ben B. Graham (2002). <i>Detail Process Charting</i>. p.2.</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFSchlager1956" class="citation journal cs1">Schlager, J. (July 1956). "Systems engineering: key to modern development". <i>IRE Transactions</i>. <b>EM-3</b> (3): <span class="nowrap">64–</span>66. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FIRET-EM.1956.5007383">10.1109/IRET-EM.1956.5007383</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:51635376">51635376</a>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFArthur_D._Hall1962" class="citation book cs1"><a href="Arthur_D._Hall" class="mw-redirect" title="Arthur D. Hall">Arthur D. Hall</a> (1962). <i>A Methodology for Systems Engineering</i>. Van Nostrand Reinhold. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-442-03046-0</bdi>.</cite> <span class="cs1-hidden-error citation-comment"><code class="cs1-code">{{cite book}}</code>: </span><span class="cs1-hidden-error citation-comment">ISBN / Date incompatibility (help)</span></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><a href="William_Gosling_(engineer)" title="William Gosling (engineer)">William Gosling</a> (1962) <i>The design of engineering systems</i>. p. 23</span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text">Tim Weilkiens (2008). <i>Systems Engineering with SysML/UML: Modeling, Analysis, Design</i>. Page 287.</span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><a href="Harold_Chestnut" title="Harold Chestnut">Harold Chestnut</a> (1967). <i>Systems Engineering Methods</i>. Page 254.</span>

</li>

<li id="cite_note-TD03-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-TD03_9-0">^</a></b></span> <span class="reference-text">Thomas Dufresne & James Martin (2003). <a rel="nofollow" class="external text" href="http://mason.gmu.edu/~tdufresn/paper.doc">"Process Modeling for E-Business"</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20061220024049/http://mason.gmu.edu/~tdufresn/paper.doc">Archived</a> December 20, 2006, at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. INFS 770 Methods for Information Systems Engineering: Knowledge Management and E-Business. Spring 2003</span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://users.jyu.fi/~jpt/ME2000/Me14/sld004.htm">Process perspectives</a>. In: <i>Metamodeling and method engineering</i>, Minna Koskinen, 2000.</span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text">James Perozzo (1994) <i>The complete guide to electronics troubleshooting</i>. p. 72</span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text">William H. Von Alven (1964) <i>Reliability engineering</i> explains: "Functional block diagrams show functional sequences and signal paths, and items which are wired in parallel are drawn in parallel" (p. 286)</span>

</li>

<li id="cite_note-SEF01-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-SEF01_13-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.dau.mil/pubs/pdf/SEFGuide%2001-01.pdf"><i>Systems Engineering Fundamentals.</i></a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070927203501/http://www.dau.mil/pubs/pdf/SEFGuide%2001-01.pdf">Archived</a> September 27, 2007, at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> Defense Acquisition University Press, 2001</span>

</li>

<li id="cite_note-faa.gov-14"><span class="mw-cite-backlink">^ <a href="#cite_ref-faa.gov_14-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-faa.gov_14-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">The first version of this article is completely based on the <a rel="nofollow" class="external text" href="http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/operations/sysengsaf/seman/SEM3.1/Section%204.4.pdf">NAS SYSTEM ENGINEERING MANUAL SECTION</a> 4.4 VERSION 3.1 06/06/06.</span>

</li>

<li id="cite_note-FAA08-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-FAA08_15-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.hf.faa.gov/webtraining/Usability/u17_tools2.htm">Task Analysis Tools Used Throughout Development</a>. FAA 2008. Retrieved 25 Sept 2008.</span>

</li>

<li id="cite_note-FAA06-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-FAA06_16-0">^</a></b></span> <span class="reference-text">FAA (2006). <a rel="nofollow" class="external text" href="http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/operations/sysengsaf/seman/SEM3.1/Section%204.4.pdf">NAS SYSTEM ENGINEERING MANUAL SECTION</a> 4.4 VERSION 3.1 06/06/06.</span>

</li>

<li id="cite_note-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-17">^</a></b></span> <span class="reference-text">IBM Corporation (1974).<i>HIPO—A Design Aid and Documentation Technique</i>, Publication Number GC20-1851, IBM Corporation, White Plains, NY, 1974.</span>

</li>

<li id="cite_note-Sandia92-18"><span class="mw-cite-backlink">^ <a href="#cite_ref-Sandia92_18-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Sandia92_18-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Sandia National Laboratories (1992). <a rel="nofollow" class="external text" href="http://www.prod.sandia.gov/cgi-bin/techlib/access-control.pl/1985/852348.pdf">Sandia Software Guidelines Volume 5 Tools, Techniques, and Methodologies</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090825000913/http://www.prod.sandia.gov/cgi-bin/techlib/access-control.pl/1985/852348.pdf">Archived</a> 2009-08-25 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> SANDIA REPORTS 85–2348qUC–32</span>

</li>

<li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19">^</a></b></span> <span class="reference-text">Mary Ann Goodwin and Charles C. Robertson (1986). <a rel="nofollow" class="external text" href="https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19880007850_1988007850.pdf">EXPERT SYSTEM VERIFICATION CONCERNS IN AN OPERATIONS ENVIRONMENT</a>. NASA paper N88-17234.</span>

</li>

<li id="cite_note-NASA95-20"><span class="mw-cite-backlink">^ <a href="#cite_ref-NASA95_20-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-NASA95_20-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">NASA (1995). "Techniques of Functional Analysis". In: <i><a rel="nofollow" class="external text" href="http://human.space.edu/old/docs/Systems_Eng_Handbook.pdf">NASA Systems Engineering Handbook</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20081217005338/http://human.space.edu/old/docs/Systems_Eng_Handbook.pdf">Archived</a> 2008-12-17 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></i> June 1995. p.142.</span>

</li>

<li id="cite_note-JM04-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-JM04_21-0">^</a></b></span> <span class="reference-text"><a href="John_Mylopoulos" title="John Mylopoulos">John Mylopoulos</a> (2004). <a rel="nofollow" class="external text" href="http://www.cs.toronto.edu/~jm/2507S/Notes04/SADT.pdf">Conceptual Modelling III. Structured Analysis and Design Technique (SADT)</a>. Retrieved 21 Sep 2008.</span>

</li>

<li id="cite_note-FL-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-FL_22-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.free-logistics.com/index.php/Download-document/22-SADT_eng.html">SADT</a> at Free-logistics.com. Retrieved 21 Sep 2008.</span>

</li>

<li id="cite_note-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-23">^</a></b></span> <span class="reference-text">Gavriel Salvendy (2001). <i>Handbook of Industrial Engineering: Technology and Operations Management.</i>. p.508.</span>

</li>

<li id="cite_note-DAC01-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-DAC01_24-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.dau.mil/pubs/pdf/SEFGuide%2001-01.pdf"><i>Systems Engineering Fundamentals.</i></a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070927203501/http://www.dau.mil/pubs/pdf/SEFGuide%2001-01.pdf">Archived</a> September 27, 2007, at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> Defense Acquisition University Press, 1999.</span>

</li>

<li id="cite_note-VG00-25"><span class="mw-cite-backlink">^ <a href="#cite_ref-VG00_25-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-VG00_25-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="Varun_Grover_(information_scientist)" title="Varun Grover (information scientist)">Varun Grover</a>, <a href="William_J._Kettinger" title="William J. Kettinger">William J. Kettinger</a> (2000). <i>Process Think: Winning Perspectives for Business Change in the Information Age. p.168.</i></span>

</li>

<li id="cite_note-AD-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-AD_26-0">^</a></b></span> <span class="reference-text">Suh (1999). Axiomatic Design: Advances and Applications, Oxford University Press, 2001, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-19-513466-4</bdi></span>

</li>

<li id="cite_note-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-27">^</a></b></span> <span class="reference-text">Paul Grefen (2010) <i>Mastering e-Business</i>. p. 5-10</span>

</li>

<li id="cite_note-28"><span class="mw-cite-backlink"><b><a href="#cite_ref-28">^</a></b></span> <span class="reference-text">US Department of Interior (2000–2008) <i>Analyze the Business and Define the Target Business Environment</i>. Accessed 27 Nov 2008.</span>

</li>

<li id="cite_note-bpmifaq-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-bpmifaq_29-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20081218223049/http://www.bpmn.org/Documents/FAQ.htm">"BPMN Information"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.bpmn.org/Documents/FAQ.htm">the original</a> on 2008-12-18<span class="reference-accessdate">. Retrieved <span class="nowrap">2008-11-02</span></span>.</cite></span>

</li>

<li id="cite_note-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-30">^</a></b></span> <span class="reference-text">Richard C. Simpson (2004). <a rel="nofollow" class="external text" href="https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20050202022_2005202152.pdf"><i>An XML Representation for Crew Procedures</i></a>. Final Report NASA Faculty Fellowship Program – 2004. Johnson Space Center.</span>

</li>

<li id="cite_note-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-31">^</a></b></span> <span class="reference-text">S.A. White, "Business Process Modeling Notation (BPMN)," In: <i>Business Process Management Initiative (BPMI)</i> 3 May 2004.</span>

</li>

<li id="cite_note-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-32">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www2.hf.faa.gov/workbenchtools/default.aspx?rPage=Tooldetails&toolID=192">Operator Function Model (OFM)</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090121030512/http://www2.hf.faa.gov/workbenchtools/default.aspx?rPage=Tooldetails&toolID=192">Archived</a> 2009-01-21 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Accessed 27 Nov 2008.</span>

</li>

</ol></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Software_engineering336" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Software_engineering336" style="font-size:114%;margin:0 4em"><a href="Software_engineering" title="Software engineering">Software engineering</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Fields</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Computer_programming" title="Computer programming">Computer programming</a></li>

<li><a href="DevOps" title="DevOps">DevOps</a></li>

<li><a href="Empirical_software_engineering" title="Empirical software engineering">Empirical software engineering</a></li>

<li><a href="Experimental_software_engineering" title="Experimental software engineering">Experimental software engineering</a></li>

<li><a href="Formal_methods" title="Formal methods">Formal methods</a></li>

<li><a href="Requirements_engineering" title="Requirements engineering">Requirements engineering</a></li>

<li><a href="Search-based_software_engineering" title="Search-based software engineering">Search-based software engineering</a></li>

<li><a href="Site_reliability_engineering" title="Site reliability engineering">Site reliability engineering</a></li>

<li><a href="Social_software_engineering" title="Social software engineering">Social software engineering</a></li>

<li><a href="Software_deployment" title="Software deployment">Software deployment</a></li>

<li><a href="Software_design" title="Software design">Software design</a></li>

<li><a href="Software_maintenance" title="Software maintenance">Software maintenance</a></li>

<li><a href="Software_testing" title="Software testing">Software testing</a></li>

<li><a href="Systems_analysis" title="Systems analysis">Systems analysis</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Abstraction_(computer_science)" title="Abstraction (computer science)">Abstraction</a></li>

<li><a href="Computer_compatibility" title="Computer compatibility">Compatibility</a>

<ul><li><a href="Backward_compatibility" title="Backward compatibility">Backward compatibility</a></li>

<li><a href="Compatibility_layer" title="Compatibility layer">Compatibility layer</a></li>

<li><a href="Compatibility_mode" title="Compatibility mode">Compatibility mode</a></li>

<li><a href="Forward_compatibility" title="Forward compatibility">Forward compatibility</a></li>

<li><a href="Software_incompatibility" title="Software incompatibility">Software incompatibility</a></li></ul></li>

<li><a href="Component-based_software_engineering" title="Component-based software engineering">Component-based software engineering</a></li>

<li><a href="Data_modeling" title="Data modeling">Data modeling</a></li>

<li><a href="Enterprise_architecture" title="Enterprise architecture">Enterprise architecture</a></li>

<li><a href="Functional_specification" title="Functional specification">Functional specification</a></li>

<li><a href="Modeling_language" title="Modeling language">Modeling language</a></li>

<li><a href="Programming_paradigm" title="Programming paradigm">Programming paradigm</a></li>

<li><a href="Software" title="Software">Software</a></li>

<li><a href="Software_archaeology" title="Software archaeology">Software archaeology</a></li>

<li><a href="Software_architecture" title="Software architecture">Software architecture</a></li>

<li><a href="Software_configuration_management" title="Software configuration management">Software configuration management</a></li>

<li><a href="Software_development_process" title="Software development process">Software development process/methodology</a></li>

<li><a href="Software_quality" title="Software quality">Software quality</a></li>

<li><a href="Software_quality_assurance" title="Software quality assurance">Software quality assurance</a></li>

<li><a href="Software_system" title="Software system">Software system</a></li>

<li><a href="Software_verification_and_validation" title="Software verification and validation">Software verification and validation</a></li>

<li><a href="Structured_analysis" title="Structured analysis">Structured analysis</a>

<ul><li><a href="Essential_systems_analysis" title="Essential systems analysis">Essential analysis</a></li></ul></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Orientations</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Agile_software_development" title="Agile software development">Agile</a></li>

<li><a href="Aspect-oriented_programming" title="Aspect-oriented programming">Aspect-oriented</a></li>

<li><a href="Object-oriented_programming" title="Object-oriented programming">Object orientation</a></li>

<li><a href="Ontology_(information_science)" title="Ontology (information science)">Ontology</a></li>

<li><a href="Service-oriented_architecture" title="Service-oriented architecture">Service orientation</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Models</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Developmental</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Agile_software_development" title="Agile software development">Agile</a></li>

<li><a href="Executable_UML" title="Executable UML">Executable UML</a></li>

<li><a href="Incremental_build_model" title="Incremental build model">Incremental model</a></li>

<li><a href="Iterative_and_incremental_development" title="Iterative and incremental development">Iterative model</a></li>

<li><a href="Software_prototyping" title="Software prototyping">Prototype model</a></li>

<li><a href="Scrum_(software_development)" title="Scrum (software development)">Scrum</a></li>

<li><a href="Spiral_model" title="Spiral model">Spiral model</a></li>

<li><a href="V-model_(software_development)" title="V-model (software development)">V-model</a></li>

<li><a href="Waterfall_model" title="Waterfall model">Waterfall model</a></li>

<li><a href="Model-driven_engineering" title="Model-driven engineering">Model-driven engineering</a></li>

<li><a href="Round-trip_engineering" title="Round-trip engineering">Round-trip engineering</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Other</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Data_model" title="Data model">Data model</a></li>

<li><a href="Entity%E2%80%93relationship_model" title="Entity–relationship model">ER model</a></li>

<li><a href="Information_model" title="Information model">Information model</a></li>

<li><a href="Metamodeling" title="Metamodeling">Metamodeling</a></li>

<li><a href="Object_model" title="Object model">Object model</a></li>

<li><a href="ISO/IEC_15504" title="ISO/IEC 15504">SPICE</a></li>

<li><a href="Systems_modeling" title="Systems modeling">Systems model</a></li>

<li><a href="View_model" title="View model">View model</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Languages</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Systems_modeling_language" title="Systems modeling language">SysML</a></li>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Systems_design" title="Systems design">Systems design</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Software_requirements_specification" title="Software requirements specification"> Requirements</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Functional_requirement" title="Functional requirement">Functional requirement</a></li>

<li><a href="Non-functional_requirement" title="Non-functional requirement">Non-functional requirement</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Capacity_planning" title="Capacity planning"> Capacity</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Active_users" title="Active users"> Users</a></li>

<li><a href="Central_processing_units" class="mw-redirect" title="Central processing units"> Compute</a></li>

<li><a href="Computer_memory" title="Computer memory"> Memory</a></li>

<li><a href="Computer_data_storage" title="Computer data storage"> Storage</a></li>

<li><a href="Bandwidth_(computing)" title="Bandwidth (computing)"> Network</a></li>

<li><a href="Web_traffic" title="Web traffic">Web traffic</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Interface_(computing)" title="Interface (computing)"> Interface</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="GraphQL" title="GraphQL">GraphQL</a></li>

<li><a href="Webhook" title="Webhook">Webhook</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="High-level_design" title="High-level design">High-level design</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Client_(computing)" title="Client (computing)"> Client</a></li>

<li><a href="Load_balancing_(computing)" title="Load balancing (computing)"> Load balancing</a></li>

<li><a href="Application_server" title="Application server">Application server</a></li>

<li><a href="Message_queue" title="Message queue">Message queue</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="System_Integration" class="mw-redirect" title="System Integration"> Integration</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Vertical_integration" title="Vertical integration"> Vertical</a></li>

<li><a href="API_management" title="API management"> API Gateway</a></li>

<li><a href="Event_store" title="Event store"> Event Source</a></li>

<li><a href="Batch_processing" title="Batch processing"> Batch</a></li>

<li><a href="Stream_processing" title="Stream processing">Stream</a></li>

<li><a href="Orchestration_(computing)" title="Orchestration (computing)"> Orchestration</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Architectures" class="mw-redirect" title="Architectures">Architectures</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Monolithic_application" title="Monolithic application"> Monolithic</a></li>

<li><a href="Microservices" title="Microservices">Microservices</a></li>

<li><a href="Event-driven_architecture" title="Event-driven architecture"> Event-Driven</a></li>

<li><a href="Client%E2%80%93server_model" title="Client–server model"> Client–server</a></li>

<li><a href="Serverless_computing" title="Serverless computing"> Serverless</a></li>

<li><a href="Circuit_breaker_design_pattern" title="Circuit breaker design pattern"> Circuit breaker</a></li>

<li><a href="Rate_limiting" title="Rate limiting">Rate limiting</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Database" title="Database">Database</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Relational_database" title="Relational database"> Relational</a></li>

<li><a href="NoSQL" title="NoSQL">NoSQL</a></li>

<li><a href="Graph_database" title="Graph database"> Graph</a></li>

<li><a href="Key%E2%80%93value_database" title="Key–value database"> Key–value</a></li>

<li><a href="Time_series_database" title="Time series database"> Time series</a></li>

<li><a href="Data_orientation" title="Data orientation"> Column Oriented</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Systems_design" title="Systems design"> Principles</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Consistency_(database_systems)" title="Consistency (database systems)">Consistency</a></li>

<li><a href="Reliability_engineering" title="Reliability engineering">Reliability</a></li>

<li><a href="CAP_theorem" title="CAP theorem">CAP theorem</a></li>

<li><a href="Software_maintenance" title="Software maintenance"> Maintainability</a></li>

<li><a href="Computer_configuration" title="Computer configuration"> Configurability</a></li>

<li><a href="Modularity" title="Modularity">Modularity</a></li>

<li><a href="Durability_(database_systems)" title="Durability (database systems)"> Durability</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Scalability" title="Scalability">Scalability</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Service_statelessness_principle" title="Service statelessness principle"> Stateless</a></li>

<li><a href="Asynchronous_I/O" title="Asynchronous I/O">Asynchronous I/O</a></li>

<li><a href="Loose_coupling" title="Loose coupling">Loose coupling</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Availability" title="Availability">Availability</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Fault_tolerance" title="Fault tolerance">Fault tolerance</a></li>

<li><a href="Failover" title="Failover">Failover</a></li>

<li><a href="Single_point_of_failure" title="Single point of failure">Single point of failure</a></li>

<li><a href="Replication_(computing)" title="Replication (computing)"> Replication</a></li>

<li><a href="Consistent_hashing" title="Consistent hashing">Consistent hashing</a></li>

<li><a href="Circuit_breaker_design_pattern" title="Circuit breaker design pattern"> Circuit breaker</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Latency_(engineering)" title="Latency (engineering)">Latency</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Cache_(computing)" title="Cache (computing)"> Cache</a></li>

<li><a href="Shard_(database_architecture)" title="Shard (database architecture)"> Shard </a></li>

<li><a href="Database_index" title="Database index">Database index</a></li>

<li><a href="Cache_prefetching" title="Cache prefetching"> Pre-caching</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Computer_data_storage" title="Computer data storage"> Storage</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Object_storage" title="Object storage">Object storage</a></li>

<li><a href="Block-level_storage" title="Block-level storage"> Block storage</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Observability_(software)" title="Observability (software)"> Observability</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Logging_(computing)" title="Logging (computing)"> Logging</a></li>

<li><a href="Software_metric" title="Software metric"> Metrics</a></li>

<li><a href="Tracing_(software)" title="Tracing (software)"> Tracing </a></li>

<li><a href="Failure_rate" title="Failure rate"> Error rate </a></li>

<li><a href="Queries_per_second" title="Queries per second">Queries per second </a></li>

<li><a href="Notification_system" title="Notification system">Notification system</a></li>

<li><a href="Anomaly_detection" title="Anomaly detection">Anomaly detection</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related fields</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Computer_engineering" title="Computer engineering">Computer engineering</a></li>

<li><a href="Computer_science" title="Computer science">Computer science</a></li>

<li><a href="Information_science" title="Information science">Information science</a></li>

<li><a href="Project_management" title="Project management">Project management</a></li>

<li><a href="Risk_management" title="Risk management">Risk management</a></li>

<li><a href="Systems_engineering" title="Systems engineering">Systems engineering</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2" style="font-weight:bold;"><div>

<ul><li><span class="noviewer" typeof="mw:File"><span title="Category"></span></span> Category</li>

<li><span class="noviewer" typeof="mw:File"><span title="Commons page"></span></span> <a href="https://commons.wikimedia.org/wiki/Category:Software_engineering" class="extiw external" title="commons:Category:Software engineering">Commons</a></li></ul>

</div></td></tr></tbody></table></div>

<div class="navbox-styles"></div><div role="navigation" class="navbox" aria-labelledby="Systems_engineering118" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Systems_engineering118" style="font-size:114%;margin:0 4em"><a href="Systems_engineering" title="Systems engineering">Systems engineering</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Subfields</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Aerospace_engineering" title="Aerospace engineering">Aerospace engineering</a></li>

<li><a href="Biological_systems_engineering" title="Biological systems engineering">Biological systems engineering</a></li>

<li><a href="Cognitive_systems_engineering" title="Cognitive systems engineering">Cognitive systems engineering</a></li>

<li><a href="Configuration_management" title="Configuration management">Configuration management</a></li>

<li><a href="Earth_systems_engineering_and_management" title="Earth systems engineering and management">Earth systems engineering and management</a></li>

<li><a href="Electrical_engineering" title="Electrical engineering">Electrical engineering</a></li>

<li><a href="Enterprise_systems_engineering" title="Enterprise systems engineering">Enterprise systems engineering</a></li>

<li><a href="Health_systems_engineering" title="Health systems engineering">Health systems engineering</a></li>

<li><a href="Performance_engineering" title="Performance engineering">Performance engineering</a></li>

<li><a href="Reliability_engineering" title="Reliability engineering">Reliability engineering</a></li>

<li><a href="Safety_engineering" title="Safety engineering">Safety engineering</a></li>

<li><a href="Stanford_torus" title="Stanford torus">Sociocultural Systems Engineering</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Processes</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Requirements_engineering" title="Requirements engineering">Requirements engineering</a></li>

<li><a href="Functional_Analysis_and_Allocation" class="mw-redirect" title="Functional Analysis and Allocation">Functional Analysis and Allocation</a></li>

<li><a href="System_integration" title="System integration">System integration</a></li>

<li><a href="Verification_and_validation" title="Verification and validation">Verification and validation</a></li>

<li><a href="Design_review" title="Design review">Design review</a></li>

<li><a href="System_of_systems_engineering" title="System of systems engineering">System of systems engineering</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Business_process" title="Business process">Business process</a></li>

<li><a href="Fault_tolerance" title="Fault tolerance">Fault tolerance</a></li>

<li><a href="System" title="System">System</a></li>

<li><a href="System_lifecycle" class="mw-redirect" title="System lifecycle">System lifecycle</a></li>

<li><a href="V-model" title="V-model">V-Model</a></li>

<li><a href="Systems_development_life_cycle" title="Systems development life cycle">Systems development life cycle</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Tools</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Decision-making" title="Decision-making">Decision-making</a></li>

<li><a href="Mathematical_optimization" title="Mathematical optimization">Optimization</a></li>

<li><a href="Quality_function_deployment" title="Quality function deployment">Quality function deployment</a></li>

<li><a href="Spare_part" title="Spare part">Spare part</a></li>

<li><a href="System_dynamics" title="System dynamics">System dynamics</a></li>

<li><a href="Systems_Modeling_Language" class="mw-redirect" title="Systems Modeling Language">Systems Modeling Language</a></li>

<li><a href="Systems_analysis" title="Systems analysis">Systems analysis</a></li>

<li><a href="Systems_modeling" title="Systems modeling">Systems modeling</a></li>

<li><a href="Work_breakdown_structure" title="Work breakdown structure">Work breakdown structure</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">People</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="James_S._Albus" title="James S. Albus">James S. Albus</a></li>

<li><a href="Ruzena_Bajcsy" title="Ruzena Bajcsy">Ruzena Bajcsy</a></li>

<li><a href="Benjamin_S._Blanchard" title="Benjamin S. Blanchard">Benjamin S. Blanchard</a></li>

<li><a href="Wernher_von_Braun" title="Wernher von Braun">Wernher von Braun</a></li>

<li><a href="Kathleen_Carley" title="Kathleen Carley">Kathleen Carley</a></li>

<li><a href="Harold_Chestnut" title="Harold Chestnut">Harold Chestnut</a></li>

<li><a href="Wolt_Fabrycky" title="Wolt Fabrycky">Wolt Fabrycky</a></li>

<li><a href="Barbara_Grosz" class="mw-redirect" title="Barbara Grosz">Barbara Grosz</a></li>

<li><a href="Arthur_David_Hall_III" title="Arthur David Hall III">Arthur David Hall III</a></li>

<li><a href="Derek_Hitchins" title="Derek Hitchins">Derek Hitchins</a></li>

<li><a href="Robert_E._Machol" title="Robert E. Machol">Robert E. Machol</a></li>

<li><a href="Radhika_Nagpal" title="Radhika Nagpal">Radhika Nagpal</a></li>

<li><a href="Simon_Ramo" title="Simon Ramo">Simon Ramo</a></li>

<li><a href="Joseph_Francis_Shea" title="Joseph Francis Shea">Joseph Francis Shea</a></li>

<li><a href="Katia_Sycara" title="Katia Sycara">Katia Sycara</a></li>

<li><a href="Manuela_M._Veloso" title="Manuela M. Veloso">Manuela M. Veloso</a></li>

<li><a href="John_N._Warfield" title="John N. Warfield">John N. Warfield</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related fields</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Control_engineering" title="Control engineering">Control engineering</a></li>

<li><a href="Computer_engineering" title="Computer engineering">Computer engineering</a></li>

<li><a href="Industrial_engineering" title="Industrial engineering">Industrial engineering</a></li>

<li><a href="Operations_research" title="Operations research">Operations research</a></li>

<li><a href="Project_management" title="Project management">Project management</a></li>

<li><a href="Quality_management" title="Quality management">Quality management</a></li>

<li><a href="Risk_management" title="Risk management">Risk management</a></li>

<li><a href="Software_engineering" title="Software engineering">Software engineering</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li>Category</li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-20" href="https://en.wikipedia.org/wiki/?title=Function_model&oldid=1301527549">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>